|
|
|
|
|
|
|
Note
For more information on debugging in Visual Basic, check out the Visual Basic Book Online. |
|
|
|
|
|
|
|
|
|
Using Visual Modeler to Add Debugging Footprints |
|
|
|
|
|
|
|
|
Adding debugging footprints (or lines of code) in your Visual Basic projects is similar to the debugging insertions provided by Class Builder, but requires that you have a model with at least one class in it. |
|
|
|
|
|
|
|
|
To try out the debug code insertion feature, open Visual Modeler. Right-click on the Logical View folder in the package browser to the left, and choose New Class from the pop-up menu. Visual Modeler inserts a new class icon in the browser with a default name of NewClass. Leave the name as is. Now choose Tools|Code Generation Wizard from the menu. Click the Next button three times. You should see the Code Generation Wizard - General Options dialog box, as illustrated in Figure 8.2. Notice in the Code Generation Options frame that the check boxes Include Debug Code and Include Err.Raise in All Generated Methods are already checked. If you're going to use your own error handling classes, you should uncheck the second check box. With Visual Basic up and running, click the Finish button. Browse the NewClass class in your project. |
|
|
|
|
|
|
|
|
Figure 8.2.
Use the Code Generation Wizard General Options dialog
box to insert debug code in your applications. |
|
|
|
|
|
